feat: Add new Discovery Phase for PM and pass product staretgy and pain points etc as context to requirement analysis#133
Conversation
…strategy and intial GTM planning ( prelim light weight)
RachnaC1234
requested review from
a team,
harmjeff,
raj-jain-aws,
scottschreckengaust and
spraja08
RachnaC1234
changed the title
| AI-DLC follows a structured three-phase approach that adapts to your project's complexity: | ||
| AI-DLC follows a structured four-phase approach that adapts to your project's complexity: | ||
|
|
||
| ### � DISCOVERY PHASE (PM-Led, Greenfield Only) |
There was a problem hiding this comment.
Non-printable character
| ### � DISCOVERY PHASE (PM-Led, Greenfield Only) | |
| ### 🟣 DISCOVERY PHASE (PM-Led, Greenfield Only) |
| ├── [project-specific structure] # Varies by project (see code-generation.md) | ||
| │ | ||
| ├── aidlc-docs/ # 📄 DOCUMENTATION ONLY | ||
| │ ├── discovery/ # � DISCOVERY PHASE (Greenfield only) |
There was a problem hiding this comment.
| │ ├── discovery/ # � DISCOVERY PHASE (Greenfield only) | |
| │ ├── discovery/ # 🟣 DISCOVERY PHASE (Greenfield only) |
scottschreckengaust
left a comment
scottschreckengaust
left a comment
There was a problem hiding this comment.
Invalid characters
|
Update the pull request title and add the contributor's statement please. Thanks! |
|
Shouldn't this be an extension, not a core change? |
RachnaC1234
changed the title
|
These workflows aim to guide the user through the three phases of the AI-DLC methodology. This PR adds a fourth phase. Regardless of merit, it's quite a big change to the project. It might be best as an extension that users can opt into, at least initially. |
|
A fundamental change in the workflow (e.g. addition of a fourth phase) I think should start from revisiting the methodology definition white paper and working backwards from there. |
|
Per the above comments, closing this PR |
5 participants
Issue #, if available:#132
*Description of changes:*Add Discovery Phase to AI-DLC for Greenfield Projects
Added a new PM-led Discovery Phase as the first phase of AI-DLC, positioned before Inception. Discovery addresses the gap where Greenfield projects jumped straight into Requirements Analysis without a structured way to identify and validate the customer problem.
*What was added:
Discovery is a top-level phase (peer to Inception, Construction, Operations) with three stages:
Envision — Gathers customer pain points through three input modes (interactive Q&A, URL/research analysis, or hybrid). The AI acts as a product strategist, asking targeted questions about target customer, current workarounds, pain severity, and willingness to change. Synthesizes findings into a categorized pain point analysis, then generates a PRFAQ using the Working Backwards method. PRFAQ questions include intelligent defaults drawn from the pain point analysis so PMs confirm or override rather than write from scratch.
Product Strategy — Captures positioning, differentiation, competitive landscape, and business model decisions. All informed by validated pain points and PRFAQ from Envision rather than assumptions.
Go-to-Market — Covers marketing strategy, sales approach, and launch planning before Construction begins.
All three stages produce a single living document (
discovery-document.md
) that Inception consumes as input context, giving Requirements Analysis a validated product definition to build upon.
Files changed:
Created:
envision.md
,
product-strategy.md
,
go-to-market.md
Deleted:
discovery.md
(replaced by the full phase)
Modified: core-workflow.md, process-overview.md, welcome-message.md, workspace-detection.md, requirements-analysis.md, workflow-planning.md, README.md
Conditional execution: Discovery only runs for Greenfield projects. Brownfield projects skip directly to Reverse Engineering / Requirements Analysis as before.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.